home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.lang.c++
- Subject: Re: OWL compiling error
- Date: 25 Feb 1996 11:34:50 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4gphgq$shu@news1.usa.pipeline.com>
- NNTP-Posting-Host: pipe14.h1.usa.pipeline.com
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Feb 24, 1996 11:25:31 in article <OWL compiling error>, 'Claus Heiko
- Niesen <cniesen@cs.iastate.edu>' wrote:
-
-
- >
- >I'm trying to compile a prewritten code and I get the error message:
- >
- >Compiling HELLOVW.CPP:
- >Fatal ..\..\..\LANGUAGE\BC45\INCLUDE\OWLCVT\OWLHDR.H 57: Error
- >directive: OWL applications must be built with WIN31 and STRICT defined.
- >
- >I checked all my help files and reference guides that came with
- >Boardland C++ Ver.4.51 but I couldn't find anything about it.
- >
- >Does anyone have a clue what the problem is?
- >
- A clue, but not a solution that I know will definitely solve your problem.
- The fact that you are invoking ..\owlcvt\anyfile.h indicates that you
- are compiling a program written with OWL 1.0 which came with BC++
- 3.x. In that version, there was a requirement to designate the target
- platforms -- either Windows 3.0 or 3.1.
-
- When building any Windows programs, it is a good idea to define
- STRICT to give you additional protection with certain handle types
- and others. Of course, it forces you to do a small amount of
- casts, but that's a small price to pay.
-
- Go into Options | Project and select Compiler | Defines. Type into
- the edit box:
-
- STRICT,WIN31
-
- and click on Ok.
-
- Then try recompiling.
-
- Good luck.
-
- --
- Pete Grant
- Kalevi, Inc.
- Software Engineering & development
-